[{"name":"Autonomos","slug":"autonomos","version":"2.0.0","author":"Jose Conti","author_profile":"https://profiles.wordpress.org/jconti/","requires":"4.0","tested":"6.3.5","requires_php":false,"requires_plugins":[],"rating":92,"ratings":{"1":0,"2":1,"3":0,"4":0,"5":6},"num_ratings":7,"support_threads":0,"support_threads_resolved":0,"downloaded":4801,"last_updated":"2023-09-25 7:29pm GMT","added":"2018-02-07","homepage":"https://www.joseconti.com","sections":{"description":"

Free version

Autonomos is a plugin developed thinking in spanish Autonomos.

What can you do with Autonomos?

Autonomos add the ability to substract the IRPF to Self Employed & Companies in the WooCommerce Checkout.
Autonomos add the CIF / NIF / NIE field to the checkout page.
Autonomos Add the ability to add product quantity to shop page & archive so buyers can add product quantity from Shop Page & Archive Page.
Autonomos Add Equivalence Surcharge.

Premium version

Compatible with Subscriptions WooCommerce extension.
Compatible with WooCommerce Rest API so any externar software can access to all data.
Comptible with PDF Invoices & Packing Slips for WooCommerce
Compatible with FacturaScripts Automatically create users and invoices in FacturaScripts from purchases in WooCommerce.

More information of Premium version here

\n","installation":"

Upload autonomos folder to the /wp-content/plugins/ directory
Activate the plugin through the ‘Plugins’ menu in WordPress
Go to WooCommerce > Settings > Autonomos and configure it.

\n","changelog":"

2.0.0

NEW: Compatibility with HPOS.
NEW: Declared compatibility with WordPress 6.3.
NEW: Declared compatibility with WooCommerce 8.0

1.4.2

FIXED: Fixed an error saving IRPF

1.4.1

FIXED: Fixed an error with DNI

1.4.0

NEW: The DNI field at the Checkout is now mandatory if user type is freelance or enterprise.

1.3.0

Added Equivalence Surcharge

1.2.0

Added an option for redirect directly to checkout when a user add a product ( the shopping cart is skipped ).
Added an option for add product quantity to shop page & archive so buyers can add product quantity from Shop Page & Archive Page
Now, the % IRPF only has 50px in the admin settings.

1.1.0.2

Unintentionally removed a return that caused a fatal error in the checkout.

1.1.0.1

Fixed a directory name that caused that Subscription template not to load (premium version).

1.1.0

Added compatibility with Subscriptions WooCommerce plugin (premium version).
CIF / NIF / NIE fields now are shown in the users profile in WordPress administration.

1.0.2

Now, IRPF is shown in the emails send by WooCommerce, in My Account and WooCommerce Orders list
Added the field CIF / NIF / NIE in the checkout.
Checkout fields rearranged in the checkout page.

1.0.1

Fixed the calculation in the checkout due to a bug in WooCommerce

1.0

First public release.

\n","screenshots":"

$\"Autonomos$
Autonomos Settings in WooCommerce
$\"Checkout$
Checkout with user selector CIF / NIF / NIE and IRPF
$\"Admin$
Admin Order with IRPF
$\"Quantity$
Quantity in Shop Page

"},"short_description":"Autonomos makes viable the use of WooCommerce by Spanish autonomos, and add tools for help them.","download_link":"https://downloads.wordpress.org/plugin/autonomos.2.0.0.zip","screenshots":{"1":{"src":"https://ps.w.org/autonomos/assets/screenshot-1.jpeg?rev=1817273","caption":"Autonomos Settings in WooCommerce"},"2":{"src":"https://ps.w.org/autonomos/assets/screenshot-2.jpeg?rev=1817273","caption":"Checkout with user selector CIF / NIF / NIE and IRPF"},"3":{"src":"https://ps.w.org/autonomos/assets/screenshot-3.jpeg?rev=1817273","caption":"Admin Order with IRPF"},"4":{"src":"https://ps.w.org/autonomos/assets/screenshot-4.jpeg?rev=1820150","caption":"Quantity in Shop Page"}},"tags":{"autonomos":"autonomos","equivalence-surcharge":"equivalence surcharge","irpf":"irpf","woocommerce":"woocommerce"},"versions":{"1.1.0.2":"https://downloads.wordpress.org/plugin/autonomos.1.1.0.2.zip","1.2.0":"https://downloads.wordpress.org/plugin/autonomos.1.2.0.zip","1.3.0":"https://downloads.wordpress.org/plugin/autonomos.1.3.0.zip","1.4.0":"https://downloads.wordpress.org/plugin/autonomos.1.4.0.zip","1.4.1":"https://downloads.wordpress.org/plugin/autonomos.1.4.1.zip","1.4.2":"https://downloads.wordpress.org/plugin/autonomos.1.4.2.zip","2.0.0":"https://downloads.wordpress.org/plugin/autonomos.2.0.0.zip","trunk":"https://downloads.wordpress.org/plugin/autonomos.zip"},"donate_link":"","icons":{"1x":"https://ps.w.org/autonomos/assets/icon-128x128.png?rev=1817273","2x":"https://ps.w.org/autonomos/assets/icon-256x256.png?rev=1817273"}},{"name":"Contasimple","slug":"contasimple","version":"1.30.0","author":"Contasimple S.L. ","author_profile":"https://profiles.wordpress.org/contasimple/","requires":"3.8","tested":"6.4.5","requires_php":"5.5","requires_plugins":[],"rating":80,"ratings":{"1":1,"2":0,"3":1,"4":0,"5":4},"num_ratings":6,"support_threads":0,"support_threads_resolved":0,"downloaded":11670,"last_updated":"2024-05-29 7:20am GMT","added":"2018-11-23","homepage":"https://www.contasimple.com/tutorial-como-configurar-plugin-woocommerce","sections":{"description":"

This plugin is an extension for your WooCommerce online shop that synchronizes automatically all generated orders to your Contasimple account.

Gain more visibility regarding your business state in real time and keep your accounting and taxes up to date.

Key features

Automatically syncs new completed orders to your Contasimple account.
You can easily export previous orders generated before the plugin installation with only a few clicks.
Configure automatic or manual email sending to your customers with attached PDF invoices from Contasimple.
Clients will be automatically created in Contasimple using WooCommerce checkout customer address information.
Configure the format for sequential numbering invoice generation, allowing to create series with custom prefixes and/or the current year in 2 or 4 digits format (ex: INV-2018-00001 or #F180000001).
Configure different numbering series to separate regular invoices, negative rectification invoices (also known as amendments, credit slips or refunds) and simplified invoices (also known as purchase receipts or tickets) as many countries have law regulations in this regard.

To learn more about the key benefits of the Contasimple platform as a whole, please check the main Contasimple Website.

Technical specifications

Requires at least WooCommerce 2.1 version. Upgrading to WooCommerce 3 or greater is strongly recommended.
Initially developed for single-site installations. Multi-site support coming soon.
Requires PHP cURL extension enabled to communicate with Contasimple’s API servers. This is common, but you might need to check it with your hosting provider.

\n","installation":"

This section describes how to install the plugin and get it working. In case of doubt, please have a look at the Screenshots section for further clarification.

Automatic installation

Automatic installation is the easiest option as WordPress handles the file transfers itself and you don’t need to leave your web browser. To do an automatic install of Contasimple for WooCommerce, log in to your WordPress dashboard, navigate to the Plugins menu and click Add New.

In the search field type Contasimple and click Search Plugins. Once you’ve found our sync plugin you can view details about it such as the point release, rating and description. Most importantly of course, you can install it by simply clicking Install Now.

Manual installation

The manual installation may be needed in certain circumstances, for example in case you have received from us a fresh new version of the plugin, not yet released on the official repository.

The traditional option is to decompress the .zip file provided by us and upload the contasimple folder to your WordPress /wp-content/plugins folder using an FTP client. The WordPress codex contains instructions on how to do this here.

Probably easier, you can also upload the zip file directly from the plugins section: navigate to the Plugins menu and click Add New, then Upload Plugin and locate the zip file on your PC (typically in your web browser download’s folder). In case of error due to either restrictive file permissions or WordPress complaining about the plugin already existing, you might need to resort to the previous described method.

Configuration

Once installed, the first thing to do is to configure the plugin to be able to connect with your Contasimple account. If you do not have a Contasimple account yet, you can register now by Clicking here.

Assuming you are already registered and have configured your fiscal region and company settings, you will be able to generate a Contasimple ‘APIKEY’. This key is unique to you and will grant your WooCommerce access to Contasimple’s servers so that the sync process can happen.

Step 1

To generate the APIKEY, you must log first into your account at Contasimple Website and then click on the Settings icon wheel on the top bar, locate the sidebar menu and scroll down to the Other options section and click External Applications. When the new section is loaded, scroll down to the bottom and you will see a Authorization keys section. Click on “+ Add authorization keyand chooseWooCommerce`.

A new key will be generated, which will look like a long sequence of random characters, something like ‘fcc6360446b04f199b715c58a9116957’. Select the key (but not the quote marks) with the help of the mouse and copy/paste it. You will need it during the next step.

Step 2

Now that we have generated the APIKEY, we need to configure the plugin to use it. All Contasimple’s plugin settings are handled by WooCommerce, since this is an integration for it. Therefore, you must navigate to WooCommerce > Settings and head to the Integration tab.

Since this is your first time using the plugin, you will be presented with the Configuration Wizard. Click on the Link account button. The first step will ask you for the previous generated APIKEY, paste the value on the text field and click Log In. You should see a success message and then you will be presented with a dialog to choose between your companies (just in case that you manage more than one) and you can also configure the correspondence between WooCommerce payment methods and Contasimple’s.

Congratulations! You have already configured the basics of the module. You can now start syncing your invoices. For more detailed info about additional configuration settings, please see the FAQ section.

\n","faq":"\n

\nHow does the synchronization exactly work?\n\n

Once the plugin has been successfully configured, every order that changes its state to ‘Completed’ will be queued to be automatically sent to Contasimple. The process might be triggered by many different means, for example, when an order is paid via a payment gateway, like Redsys, or when you manually mark an order as completed in the back-office, once you have verified a payment via bank transfer.

Most likely the order will be immediately sent to Contasimple when the order status changes. However, in case an invoice cannot be instantly sent, due to either a high number of incoming orders to process or for whatever other reason, the process will be resumed again each time an order reaches the shop, until the queue is empty and all orders are sent.

You can check the sync status for all completed orders at any moment on the Invoices section that the plugin will add to your WooCommerce menu entry.

\nI already have orders in my shop. Will I be able to sync them?\n\n

Yes. While the plugin will automatically handle all new orders of the shop, you can export all previous orders by navigating to the WooCommerce > Invoices section and clicking the Create from previous orders button.

You will be presented with a page that lists all completed orders that have not yet been queued for sync, this of course includes orders prior installing the plugin. You can check some or all of them and then pick the Create action from the actions dropdown list that appears on top.

Orders added this way will not be synced automatically right now, but they will be added to the sync queue. Hence you can let the plugin send them automatically when a new order is completed or, if you want to sync right now, you can always navigate back to the Invoices page and manually trigger the process by clicking the Sync now button.

Notice that in this screen you can filter invoices by fiscal periods. This might interest you in case that you want to add to sync all the invoices for an ongoing tax collection period, but do not want to do further action with already declared invoices from previous fiscal periods.

\nHow does the invoice numbering system work?\n\n

In contrast to other eCommerce platforms, WooCommerce does not do sequential numbering from the get go, but uses WordPress internal post identification system. Sharing ID with blog post and many other types of content means no sequential numbering is possible by default.

To solve this, Contasimple will keep the count of your synced orders and will assign the next sequential number any time an invoice is successfully synced, based on the mask assigned to the corresponding invoice series.

Masks can be customized on the WooCommerce > Settings > Integrations page. There are three configurable masks for regular invoices, negative rectification invoices (for refunds) and simplified invoices (tickets) since many countries, like Spain, have fiscal laws that require to keep track of each type separately.

By default, each one is set at different values, so that you will be working with three different series for each type of scenario. However, you could play with this and set the same value for both regular invoices and simplified invoices, or even for refunds as well, to make them fall into the same series in case that you prefer it and your country does not have any particular requirement on this.

To know how to form the desired mask, please log into Contasimple website and go to Settings > Invoices, there you will find more information and examples.

\nHow does the invoice emailing feature work?\n\n

This plugin uses WooCommerce built-in emailing system to deliver the invoice emails to your customers. If you go to WooCommerce > Settings > Emails you will see that you have a new type of email listed Order invoice. Like all WC email types, you can enable or disable it here and also change a few things, like the default subject or if you want it to be a plain text email or a fully fledged HTML template.

Default templates provided for the Contasimple invoice emails include only a brief message and the generated invoice PDF as a file attachment because the default WC Completed Order email template already has an item summary and we feel that it would be redundant to include this info again. However, if you want -and know how to- you could customize the templates to suit your needs.

Something to keep in mind is that, even if the invoice emails are set to enabled, only orders completed during the last 24 hours will be emailed automatically to your customers. We have set this restriction to avoid potential unwanted situations, like syncing all your previous year invoices just for historic purposes and then having all your customers emailed out of nowhere.

You can always send an invoice manually as many times as you consider it necessary to a certain customer, by going to the plugin Invoices section and clicking the email action button for the desired invoice.

\nI already have a plugin that handles these or other invoicing feature, can I work with both?\n\n

It really depends, but most likely no.

As described in a previous section, Contasimple handles invoice numbering sequence in a very specific way, which is unaware of other installed plugins and which, conversely, does not expect other plugins to hook into it. Therefore, if you have other plugins installed, most likely you will end generating duplicated invoices for your orders and with totally different numbering series.

If you finally decide to use the Contasimple plugin to generate legally compliant invoices for your orders, we strongly recommend to disable all other invoicing plugins that you might be trying or using during the past.

If you feel that we are missing some very cool feature present in other plugins that ties particularly to tax legislation, feel free to contact us to suggest it and we will consider it.

\nI already synced previous orders and I see they have a strange 4 digit prefix in them. What does that mean?\n\n

Previous orders added manually to the sync queue use the configured mask under Contasimple settings, but will also add a random prefix to it. This is not configurable and it is done as a safety mechanism to avoid breaking fiscal laws.

Most countries require invoice numbering series to be sequential but also to respect issuing order. Imagine that you install and configure the plugin and get a few incoming orders that get instantly synced to your Contasimple account, but then you decide to have a look at the existing orders for the whole current year and want to sync them as well. You would end with an incorrect issuing sequence.

This is why Contasimple adds a random prefix each time a manual invoice creation is performed. This means you can end with a few different batches of invoicing series, which might seem not ideal. However, most countries fiscal laws allow to have different invoicing series if it can be justified, as long as the issuing order for each series is respected.

\nI understand the previous point, but I really, REALLY want to have a unique series for all my invoices. Is there any way I could achieve that?\n\n

With some limitations, yes. Assuming you have still not synced any invoice to Contasimple or that you can delete in Contasimple Web the already uploaded ones so that you can start back from scratch, you can:

(Optional) Disable your shop to avoid any orders to sync automatically during this process. WooCommerce does not allow this by default but there are plugins that allow you to.
Set the desired numbering series format in WooCommerce > Settings > Integrations > Contasimple keeping in mind that 4 additional random numbers will be added first during the already existing orders sync process.
Navigate to the Create from previous orders, mark as selected all the desired orders and click Create from the bulk actions drop-down control as described previously.
Navigate back to Invoices and click the Sync now button.
The page will reload with the sync results (might take some time).
If all invoices are synced OK, you can proceed to next step. In case there were any errors present, they must be solved before continuing so that you do not miss any invoice (see the next FAQ section).
Once all previous orders have been synced, write down (or just copy/paste) the 4 random digits appended to all invoices.
Finally, you can go back to the plugin settings and modify your numbering series mask format to add these 4 digits before the already defined masks. This way, all new incoming orders will respect the same series when their status changes to Completed. Just keep in mind that anytime that you add previous existing orders to the queue, the plugin will create a new series to avoid the aforementioned numbering sequence mismatch.

\nMy store sells internationally and allows payments with more than one currency (not just with translations). Is this supported?\n\n

Unfortunately, no. Or at least not without some additional work from your side.

Contasimple only works with the currency configured in Contasimple Web for the desired fiscal region, since most countries mandate to declare taxes with its own currency. If you try to sync orders paid with a currency different than the one configured for your fiscal region, you will get an error.

Accounting conciliation due to currency conversion is out of the scope of the plugin and you should configure your multi-currency plugin to work internally with only one currency, like WooCommerce does by default, and then try to sync to Contasimple.

Note that, in its documentation, WooCommerce also recommends to work with only one currency internally (as it does by default) and handle multiple currencies for the customers by showing estimated conversions via the Currency Converter Widget.

\nIs WordPress Multisite (Network installation) supported?\n\n

At the time of release we only support single-site mode. However, we are already working on bringing multisite support and it should be available soon.

\nWe get an Error 504 (Gateway Time Out) after a minute or so when trying to sync invoices. What’s going on?\n\n

Most web hosting servers have a certain timeout set to abort long-lasting processes in order to save resources. If you have a lot of invoices pending to sync and depending on your server configuration, you might not be in time to sync all of them at once. The process will abort after a certain time passes (sometimes as short as 30 seconds) and you will get the infamous 504 error.

If you have a dedicated VPS you might be able to configure Apache/Nginx timeout variable settings to greater values (ex: 5 minutes). You might be able to do so also on some premium shared web hosting services.

In any case, you can always restart the syncing process from the Invoices section (or just wait for a new order to be completed) and the syncing queue will resume, so you will be able to sync all invoices eventually. However, we would recommend a quality hosting service where a sysadmin can fine-tune the settings to suit your goals.

\nThere are invoices showing errors on the `Invoices` page. What can I do?\n\n

Errors during the sync process might occur due to several reasons:

Invalid invoicing data. This is the most common case. For example: a customer entered the NIF with an invalid format during the checkout process or VAT types applied are incorrect for your fiscal region.
Server downtime either on your web server side or on Contasimple side, which will not allow to establish a connection. This might happen due to maintenance tasks or ISP provider shortage.
Unexpected technical issues. For example:\n
- A WooCommerce/WordPress version that has a bug or a deprecated/missing feature not accounted for, which might cause the plugin to break.
- 3rd party plugins that might interfere with ours.
- Very specific web server settings that cause incompatibilities (PHP unsupported version, Apache/Nginx restrictive policies, Javascript conflicting libraries or file system permissions).
\n

If an error occurs due to invalid invoicing data or other well-known causes, Contasimple will inform you and you will either have to edit the order/customer details or configure your shop with the correct settings so that the invoice can be safely synced.

For example, if VAT rate changes occur the next year and your shop is not up to date when an order completes, you will receive an error during the sync process. You will see an Invalid VAT type for your fiscal region error and you will need to configure the VAT correctly for that specific region before being able to sync OK, which avoids potential fiscal issues and helps you improve your online business invoicing compliance with your country’s fiscal law.

In case you see an Unknown Error it will mean that the error probably occurred due to technical difficulties during the syncing process. We would advise you to try the syncing process again later, just in case there was a temporary connection problem on either side. However, if the syncing fails systematically every time you try to sync some or all of your invoices, there might be a technical issue that is preventing the plugin to work correctly and will need further assistance. In that case, please contact us so that we can help you troubleshoot your issue.

Our team might request you to provide an error log file which will help us gathering crucial information to detect the root cause. To obtain this error file, you can either:

Download it easily from the WooCommerce > Settings > Integrations > Contasimple page at the Log section. Please select the desired date when you found an issue and click the Download button.
Get the file directly from your hosting via FTP or File Manager on your cPanel/Plesk admin panel or similar. The file will be located under the WordPress modules folder, more precisely at: /wp-content/plugins/woocommerce-contasimple and will have a name format similar to contasimple_30-12-2017.log.

\nSome invoices are synced with different concept lines than the original order in WooCommerce, grouped by VAT type. Why it happens?\n\n

Contasimple and WooCommerce represent differently the prices of the products and applied taxes. While Contasimple always works with two decimal places, WooCommerce allows you to configure the number of decimal places that we want to appear on the screen (by default they are two, as in Contasimple) but internally it works with six decimal places in almost all its calculations and only stores the numbers with two decimal places for the auto-calculated values of the total amount with and without taxes of the entire order.

This difference in the internal representation of decimal numbers causes that, on some occasions, when transferring the amounts of WooCommerce products to Contasimple the invoice total amount may not match with respect to the original order.

Let’s see an example to understand it better:

Suppose that our store sells a product of which many units are usually sold per order at a price of 0.99 euros per unit, taxes already included. WooCommerce allows the option of entering the prices of the products with VAT already included, so that WooCommerce itself calculates the resulting tax base so that, once the VAT corresponding to the default country of the store has been applied, the final price of the unit is €0.99.

If a customer buys a single unit of our product in Spain and 21% VAT is applied, in this example the price that WooCommerce will calculate to adjust the tax base to the amount we want to invoice the user with taxes included will be 0.99 / 1.21 = 0.818181 euros. The amount of VAT applied to the product will therefore be the remaining (0.171818 euros). You can read more information about tax calculation on this official WooCommerce page (https://github.com/woocommerce/woocommerce/wiki/How-Taxes-Work-in-WooCommerce).

As WooCommerce shows the prices on the screen already rounded to the default number of digits, in the shopping cart we would see 0.82 euros for the base and 0.17 euros for VAT, and a total of 0.99 euros. This type of order could be correctly synchronized with Contasimple because even while rounding the prices to two decimal places before adding the amounts, the result is the same (no error accumulates).

Now suppose that another user buys 100 units of the same product.

The calculation that WooCommerce performs internally to calculate the totals is as follows:

Unit Price: 0.818181
\nUnits: 100
\nTotal tax base: 81.818181 (81.82 is displayed on the screen)
\nAmount 21% VAT: 17.181818 (17.18 is displayed on the screen)
\nTotal: 98.999999 (99 is displayed on the screen and 99.00 is also saved as the final amount)

As we can see, WooCommerce makes use of the 6 decimal places in all its calculations regardless of whether it shows rounded prices on the screen.

However, when the plugin tries to transfer these values to the Contasimple invoice, it first has to round all the components of the invoice line to two decimal places, and then carry out the calculations so, in the end, the invoice line in Contasimple becomes:

Unit price: 0.82 (already rounded)
\nUnits: 100
\nTotal tax base: 82.00
\nAmount 21% VAT: 17.22
\nTotal: 99.22

If these amounts were ever to be synchronized, a difference of 22 cents would accumulate (18 cents would come from the price without taxes and 4 cents from the VAT) with respect to the original order due to the slight difference in rounding of decimals that occurs in the unit of the product. This difference is further aggravated if the order contains other products that also accumulate rounding errors.

Contasimple prioritizes at all times that the amounts transferred for the taxable base totals and VAT are accurate with respect to those of the original order to ensure that the user accounting is never out of balance and to avoid incorrect values to be ever declared to the Tax Agency. Therefore, the plugin can resort to the strategy of reorganizing the invoice lines in order to apply rounding at the end of the calculation and thus be able to minimize calculation errors and synchronize the invoice with the exact original amounts.

For example, if the previous invoice line is reformulated by taking the total price of 100 units and introducing it as a single unit, we can see that the new total amount in the invoice line in Contasimple matches the original order item:

Unit price: 81.82 (0.818181 * 100, rounded)
\nUnits: 1
\nTotal tax base: 81.82
\n21% VAT amount: 17.18
\nTotal: 99.00

This invoice can be safely synchronized to Contasimple since it does not cause any accounting mismatches.

Note: Since version 1.8 of the plugin, all the information of the original order is transferred to the comments of each invoice line, so that the end customer will always see the information of the original order in WooCommerce and no details will be lost.

This situation can be avoided in the vast majority of cases by applying the following recommended settings to your WooCommerce store:

1 – Configure WooCommerce to enter product prices without taxes.

This is the default option and it is recommended to keep it this way unless it is imperative (for example, in the case of wanting to sell a product at a single price globally, regardless of the rates applied amongst different countries / fiscal regions).

To return to the default option you must go to the menu ‘WooCommerce > Settings > Taxes > Prices with taxes included’, select the option ‘No, I will enter the prices without taxes’ and click on ‘Save the changes’.

In the event that you want your customers to view prices with VAT included regardless of whether they are entered without VAT in the store, there are two other settings in this same section that can help you: ‘Show prices in the store’ and ‘Show prices in the cart and at checkout’. In both cases, select the option ‘VAT included’ if applicable. These two options do not affect the internal calculation of the amounts.

2 – Configure WooCommerce to apply rounding at line level.

This is also the default option and it is recommended to keep it with the default value as it replicates more accurately the rounding system applied by Contasimple (for each field) and therefore makes it easier for the invoice to be synchronized to contain fewer rounding errors.

To return to the default option you must go to the menu ‘WooCommerce > Settings > Taxes > Rounding’ and uncheck the box ‘Rounding of tax in the subtotal, instead of rounding for each line’.

3 – Review the pricing policies of the existing products in the store.

If you have the flexibility to define the prices of the products in your catalog, then we recommend that you use as few decimal places as possible to minimize the probability of rounding errors, trying never to use more than two decimal places. In other words, prices must be set in such a way that the unit tax base is representable to two decimal places, without the need for rounding.

If you had previously activated the setting to enter the prices of products with taxes already included and you change it to work in the recommended way, you must bear in mind that the change will apply only to the new products that you register from now on and to new orders placed in the store. Therefore, you should review the existing products and edit the prices taking into account that VAT will now be applied later during the purchase process.

\nWhy are some invoices associated with a customer called Multiple customers instead of their original customer?\n\n

This happens as long as the user who makes the purchase in the store has not filled in the NIF field (or the equivalent field in the fiscal region that you have configured in your company in Contasimple).

In Contasimple, every client must have the NIF field filled in, since it is mandatory for the client to be eligible as the target of a fiscally valid invoice.

When a WooCommerce order is synchronized to Contasimple, the plugin creates an invoice and associates it with the customer with the same NIF that exists in Contasimple, and if it does not exist it tries to create it from the data provided in the filled out ‘Billing details’ fields by the user in the WooCommerce purchase form.

By default, WooCommerce does not include a field to enter the ‘Tax Identifier / NIF’ during the purchase process, so the plugin creates it during its installation, however, filling in this field is not mandatory during the purchase process, since many customers of the online store may be individuals who do not want the order invoice and who do not want to provide this information either.

This scenario would be equivalent to making a purchase in a physical store, in which the customer can request an invoice and to do so provide all their data (including the fical identifier / NIF) to the seller, or they can choose to take the sales ticket as proof of the transaction (also known as a simplified invoice), which identifies the seller and the products sold but not the buyer.

However, when synchronizing that sale order with Contasimple, it requires that a tax identifier or customer NIF is specified, therefore, in the event that the customer has not provided a value, the plugin ignores the fields filled in by the user in the WooCommerce checkout form and instead associates the order with a fictitious customer called ‘Multiple customers’, equating that invoice to a purchase receipt.

These invoices are treated by the program as if they were sales tickets, and are synchronized in a separate series, which can be configured in the ‘Settings’ menu of the Contasimple plugin for WooCommerce.

In case your online commerce is only ‘B2B’ or you simply want to always request the NIF field from all your clients, since version 1.9 of the plugin you can configure the NIF field to be mandatory, so that all clients must enter it in order to finalize the purchase process. In this way you can prevent invoices from being synchronized without information from your customers.

You will find this setting in the plugin settings section (WooCommerce > Settings > Integration > Contasimple). You just have to check the box ‘NIF / Company identifier mandatory’ and save the changes.

If the customer that will be used to group sales orders to customers without a VAT number has not been previously configured, the plugin will try to configure it automatically when synchronizing the first order, and assigns it by default the name ‘Multiple customers’ and the fictitious VAT number ‘00000000X’. If you already had a client registered in Contasimple previously with this NIF, when synchronizing the invoice you will be informed that said client cannot be generated and the synchronization will fail until you configure it manually from the Contasimple website. You can create said client manually, change its name or even the NIF from the Configuration -> Taxes screen of the Contasimple website, in the ‘Invoices to unidentified clients’ section.

\n\n","changelog":"

1.30.0

Fixes not being able to create invoices from previous orders if HPOS is enabled.

1.29.0

Some bug fixes and code improvements.

1.28.0

New: Compatibility with HPOS.
Some bug fixes and code improvements.

1.27.0

Some bug fixes and code improvements.

1.26.0

Fixes synchronization issues in some edge-cases (regarding partial refunds and rounding issues).
Improvements in invoice concurrency sync control.

1.25.0

Added setting to enable/disable concurrency control checks.
Some bug fixes and code improvements.

1.24.0

Some bug fixes and code improvements.

1.23.0

Some bug fixes and code improvements.

1.22.0

Updated integration with the external VIES validation service.
Some bug fixes and code improvements.

1.21.0

Some bug fixes and code improvements.

1.20.0

Some bug fixes and code improvements.

1.19.0

New: You can now configure the plugin to sync the invoices when orders enter the default ‘On-Hold’ status.

1.18.0

Some bug fixes and code improvements.

1.17.0

Some bug fixes and code improvements.

1.16.0

New: The plugin now uses the in-built Contasimple numbering series feature.

1.15.0

Some bug fixes and code improvements.

1.14.0

Some bug fixes and code improvements.

1.13.0

New: You can now customize the text that will be displayed in the NIF field.
Some bug fixes and code improvements.

1.12.0

Some bug fixes and code improvements.

1.11.0

New: You can now configure the plugin to sync the invoices when orders enter the ‘Processing’ status. Until now, invoices could only be synced when the orders were marked as ‘Completed’.
Some bug fixes and code improvements.

1.10.0

Some bug fixes and code improvements.

1.9.0

New: You can now set the NIF / company identifier field to be required during the checkout process (configurable via the settings section).

1.8.0

New: In those invoices that need to be grouped by VAT percentages due to rounding issues, you will now see a description of the original items in the advanced notes for each invoice line.
Fixes the ‘Missed schedule’ issue during invoice sync in some installations depending on how the timezone and server time is set.
Fixes an issue syncing an invoice if the value of a tax rate is changed after the order has been created.

1.7.0

New: Discount coupons are now reflected in the Contasimple invoice (only in WooCommerce 3.2 or greater).
New: You can now sync more than one partial refund for a given order (does not apply to the import from previous orders feature).
New: You can now sync previously failed invoices individually (beware though, they will use a different numeric series).
New: You can now opt to pass the product SKU to the invoice line concept (configurable via the settings section).
Fixes errors with the latest PHP 7.4 version.
Some other bug fixes and code improvements.

1.6.0

New: Displaying of customer billing address and NIF / company number in the invoice sync page.
New: Support for intracommunitary invoices for customers that have a valid VIES number.
Some bug fixes and code improvements.

1.5.0

Fixes an error where the plugin would disconnect due to lack of connection or incompatibility issues.

1.4.2

New: Order fees are now synchronized automatically.
New: Possibility to remove pending invoices from sync queue.
New: Sync attempts while in error state fixed to 3 (on automatic sync) and the error email will only be sent once.
Many fixes and code improvements regarding the sync process and invoice amounts calculations.

1.4.1

State/province from customer checkout address is now synced to Contasimple.
Other bug fixes and code improvements.

1.4.0

New: Supports the special regime for additional VAT (RE) and IRPF taxes (Spain only).
New: Emails the shop owner when an order synchronization fails.
New: Allows the synchronization process to keep syncing incoming orders even if the synchronization of a previous order failed.
Fixes compatibility issue with PHP version 7.3
Fixes issue syncing invoices with negative amounts (refunds)
Other minor bug fixes.

1.3.1

Minor bug fixes.

1.3.0

Updated plugin to support the latest multiuser feature on Contasimple.
Updated plugin to natively support the equivalence surcharge tax.
Other minor bug fixes.

1.0.4

Minor bug fixes.

1.0.3

Minor bug fixes.

1.0.2

Mandatory update to adapt to Contasimple API changes in country settings.

1.0.1

Fixes bug during plugin activation if server PHP version is older than 5.6.

1.0

Initial release of the plugin.

\n","screenshots":"

$\"Settings$
Settings screen. Linking you Contasimple account (step 1).
$\"Settings$
Settings screen. Entering your APIKEY (step 2).
$\"Settings$
Settings screen. Picking your company (step 3).
$\"Settings$
Settings screen. Picking your payment methods (step 4).
$\"Settings$
Settings screen. Linked account info summary and unlinking options (if reconfiguration is needed).
$\"Settings$
Settings screen. Numbering series format masks for regular invoices, negative invoices (refunds) and simplified invoices (tickets).
$\"Settings$
Settings screen. Error log file downloading for customized troubleshooting with Contasimple technical team.
$\"Invoices$
Invoices screen. Empty screen showing there are no new completed orders since activation. Previous orders can be imported by clicking the Create from previous orders.
$\"Import$
Import screen. Selecting the desired fiscal period.
$\"Import$
Import screen. Selecting all filtered orders at once via the global checkbox control. Select Create from the dropdown list and hit Apply to start.
$\"Import$
Import screen. Success message after orders are imported. You can go back to Invoices to see the pending sync queue.
$\"Invoices$
Invoices screen. Pending invoices. Will be automatically synced once a new order completes, or you can manually Sync pending now to trigger the process immediately.
$\"Invoices$
Invoices screen. All invoices are synced successfully. You can perform actions on the right (open in Contasimple Web, Download PDF and send email with PDF to customer).
$\"Invoices$
Invoices screen. Sending an invoice PDF to a customer manually.

"},"short_description":"This module allows you to export all WooCommerce orders as invoices in Contasimple.","download_link":"https://downloads.wordpress.org/plugin/contasimple.1.30.0.zip","screenshots":{"1":{"src":"https://ps.w.org/contasimple/assets/screenshot-1.png?rev=1980741","caption":"Settings screen. Linking you Contasimple account (step 1)."},"2":{"src":"https://ps.w.org/contasimple/assets/screenshot-2.png?rev=1980741","caption":"Settings screen. Entering your APIKEY (step 2)."},"3":{"src":"https://ps.w.org/contasimple/assets/screenshot-3.png?rev=1980741","caption":"Settings screen. Picking your company (step 3)."},"4":{"src":"https://ps.w.org/contasimple/assets/screenshot-4.png?rev=1980741","caption":"Settings screen. Picking your payment methods (step 4)."},"5":{"src":"https://ps.w.org/contasimple/assets/screenshot-5.png?rev=1980741","caption":"Settings screen. Linked account info summary and unlinking options (if reconfiguration is needed)."},"6":{"src":"https://ps.w.org/contasimple/assets/screenshot-6.png?rev=1980741","caption":"Settings screen. Numbering series format masks for regular invoices, negative invoices (refunds) and simplified invoices (tickets)."},"7":{"src":"https://ps.w.org/contasimple/assets/screenshot-7.png?rev=1980741","caption":"Settings screen. Error log file downloading for customized troubleshooting with Contasimple technical team."},"8":{"src":"https://ps.w.org/contasimple/assets/screenshot-8.png?rev=1980741","caption":"Invoices screen. Empty screen showing there are no new completed orders since activation. Previous orders can be imported by clicking the Create from previous orders."},"9":{"src":"https://ps.w.org/contasimple/assets/screenshot-9.png?rev=1980741","caption":"Import screen. Selecting the desired fiscal period."},"10":{"src":"https://ps.w.org/contasimple/assets/screenshot-10.png?rev=1980741","caption":"Import screen. Selecting all filtered orders at once via the global checkbox control. Select Create from the dropdown list and hit Apply to start."},"11":{"src":"https://ps.w.org/contasimple/assets/screenshot-11.png?rev=1980741","caption":"Import screen. Success message after orders are imported. You can go back to Invoices to see the pending sync queue."},"12":{"src":"https://ps.w.org/contasimple/assets/screenshot-12.png?rev=1980741","caption":"Invoices screen. Pending invoices. Will be automatically synced once a new order completes, or you can manually Sync pending now to trigger the process immediately."},"13":{"src":"https://ps.w.org/contasimple/assets/screenshot-13.png?rev=1980741","caption":"Invoices screen. All invoices are synced successfully. You can perform actions on the right (open in Contasimple Web, Download PDF and send email with PDF to customer)."},"14":{"src":"https://ps.w.org/contasimple/assets/screenshot-14.png?rev=1980741","caption":"Invoices screen. Sending an invoice PDF to a customer manually."}},"tags":{"accounting":"Accounting","billing":"Billing","contasimple":"contasimple","invoicing":"invoicing","taxes":"taxes"},"versions":{"1.0.1":"https://downloads.wordpress.org/plugin/contasimple.1.0.1.zip","1.0.2":"https://downloads.wordpress.org/plugin/contasimple.1.0.2.zip","1.0.3":"https://downloads.wordpress.org/plugin/contasimple.1.0.3.zip","1.10.0":"https://downloads.wordpress.org/plugin/contasimple.1.10.0.zip","1.11.0":"https://downloads.wordpress.org/plugin/contasimple.1.11.0.zip","1.12.0":"https://downloads.wordpress.org/plugin/contasimple.1.12.0.zip","1.13.0":"https://downloads.wordpress.org/plugin/contasimple.1.13.0.zip","1.14.0":"https://downloads.wordpress.org/plugin/contasimple.1.14.0.zip","1.15.0":"https://downloads.wordpress.org/plugin/contasimple.1.15.0.zip","1.16.0":"https://downloads.wordpress.org/plugin/contasimple.1.16.0.zip","1.17.0":"https://downloads.wordpress.org/plugin/contasimple.1.17.0.zip","1.18.0":"https://downloads.wordpress.org/plugin/contasimple.1.18.0.zip","1.19.0":"https://downloads.wordpress.org/plugin/contasimple.1.19.0.zip","1.20.0":"https://downloads.wordpress.org/plugin/contasimple.1.20.0.zip","1.21.0":"https://downloads.wordpress.org/plugin/contasimple.1.21.0.zip","1.22.0":"https://downloads.wordpress.org/plugin/contasimple.1.22.0.zip","1.23.0":"https://downloads.wordpress.org/plugin/contasimple.1.23.0.zip","1.24.0":"https://downloads.wordpress.org/plugin/contasimple.1.24.0.zip","1.25.0":"https://downloads.wordpress.org/plugin/contasimple.1.25.0.zip","1.26.0":"https://downloads.wordpress.org/plugin/contasimple.1.26.0.zip","1.27.0":"https://downloads.wordpress.org/plugin/contasimple.1.27.0.zip","1.28.0":"https://downloads.wordpress.org/plugin/contasimple.1.28.0.zip","1.29.0":"https://downloads.wordpress.org/plugin/contasimple.1.29.0.zip","1.30.0":"https://downloads.wordpress.org/plugin/contasimple.1.30.0.zip","1.6":"https://downloads.wordpress.org/plugin/contasimple.1.6.zip","1.6.0":"https://downloads.wordpress.org/plugin/contasimple.1.6.0.zip","1.7.0":"https://downloads.wordpress.org/plugin/contasimple.1.7.0.zip","1.9.0":"https://downloads.wordpress.org/plugin/contasimple.1.9.0.zip","trunk":"https://downloads.wordpress.org/plugin/contasimple.zip"},"donate_link":"","icons":{"1x":"https://ps.w.org/contasimple/assets/icon.svg?rev=1980741","svg":"https://ps.w.org/contasimple/assets/icon.svg?rev=1980741"}},{"name":"PayGreen Impact","slug":"paygreen-impact","version":"1.3.7","author":"WattIsIt","author_profile":"https://profiles.wordpress.org/paygreen/","requires":"4.0","tested":"6.0.9","requires_php":"5.2.0","requires_plugins":[],"rating":40,"ratings":{"1":0,"2":1,"3":0,"4":0,"5":0},"num_ratings":1,"support_threads":0,"support_threads_resolved":0,"downloaded":1676,"last_updated":"2023-06-13 9:38am GMT","added":"2021-12-29","homepage":"http://www.paygreen.io","sections":{"installation":"

This section describes how to install the plugin and get it working.

e.g.

Upload the plugin files to the /wp-content/plugins/plugin-name directory, or install the plugin through the WordPress plugins screen directly.
Activate the plugin through the ‘Plugins’ screen in WordPress
Use the Settings->Plugin Name screen to configure the plugin
(Make your instructions match the desired user flow for activating and installing your plugin. Include any steps that might be needed for explanatory purposes)

\n","changelog":"

4.10.4 – 24.05.2023

Erreur à la récupération du carrier au moment du paiement.

4.10.3 – 08.03.2023

Méthode ‘get_cart_hash’ manquante pour certaines versions de woocommerce.

4.10.2 – 27.01.2023

Correction d’une erreur lors de la validation d’un don.

4.10.1 – 20.10.2022

Prise en compte des taxes et des frais de livraisons pour le calcul du don.
Supprimer la variation de produit inutile du don.

4.10.0 – 22.02.2022

Mettre à jour la vignette Paiement.
Equivalence des moyens de livraison.
Ajout du formulaire de personnalisation du bandeau de contribution carbone.
Affichage de la prévisualisation du bandeau de contribution carbone.
Simplification du formulaire d’affichage du CarbonBot.
Ajouter traduction dynamique du bandeau de contribution.
Mise à jour du design du bandeau charity.
Ajout d’un bouton pour rafraichir la liste des associations partenaires.
Amélioration du bandeau Charity pour l’affichage des dons.
Correction d’une erreur sur la page de paiement.
Correction commandes validées, mais non payés dans certains cas.
Gestion des statuts de commandes inconnus considérant la commande comme payée.
Corrections de traductions manquantes.
Correction d’une erreur lors de la mise à jour du module sur les versions 5 de php.
Récupérer correctement le groupe par défaut ou la liste des associations si pas de groupe par défaut.
Ne pas afficher le bandeau Charity quand aucune association n’est partenaire.
Correctif pour empêcher l’ajout d’un don ou de la contribution au dossier carbone.
Correctif pour ajouter correctement un don lors d’un IPN.
Possibilité d’ajouter un overlay derrière l’iframe de paiement.

4.9.0 – 05.11.2021

Archivage régulier des logs trop volumineux.
Ajout d’une page de gestion du planificateur interne.
CharityKit : refonte complete de la page de gestions des traductions.
Nouveau dashboard impact (CharityKit et ClimateKit).
Notification adresse d’expédition requise pour ClimateKit.
Nouveau dashboard pour le bloc de Paiement.
Ajout des catégories et prix dans l’export du catalogue.
Nouveau CarbonBot.
Modification administration CarbonBot.
Ajout produit Climate contribution au panier.
Affichage en mode test dans le bloc de contribution.
Corriger retours pour validation.
Corriger l’upgrade FixGreenAccessTokenSettingUpgrade.
Erreur à l’enregistrement d’une traduction dynamique.
Correction du module de confirmation de click.

4.8.3 – 22.12.2021

4.8.2 – 24.11.2021

4.8.1 – 16.11.2021

Possibilité d’exporter directement le catalogue produit vers l’api ClimateKit.
Retirer le filtre d’échapemment sur les variables de templates qui retourne du HTML.
L’export direct du catalogue produit ne fonctionne pas si ClimateKit n’est pas SOFT activé.

4.8.0 – 09.11.2021

Revoir l’affichage du nom du serveur des produits sur la page de support.
Arrondir le bilan carbone du carbon bot.
Arrondir et mettre en avant le bilan carbone sur la page de confirmation de commande.
Modifier l’affichage du Charity block pour afficher directement l’association lorsqu’une seule est disponible.
Ne pas compiler les bundles de dev en environnement IMPACT.
Suppression de l’installation/désinstallation de la table ‘fingerprint’.
Suppression de la double gestion du setup de la table ‘setting’.
Corrections des anciens upgrades.
Configuration d’upgrades pour modifier les serveurs utilisés par les API.
Si un produit n’a pas de référence, utiliser son identifiant boutique pour contacter l’api ClimateKit.
Corriger la traduction anglaise pour les données web du CarbonBot.
Mauvais tokens utilisés après avoir régénéré un nouveau jeu de tokens.
Le bilan carbone n’est pas affiché en gras si le CarbonBot n’est pas activé.
Retirer les requirements sur la route ‘front.charity.gift_explanation’.
Configurer un upgrade pour modifier le serveur utilisé par les API.
Corriger les upgrade de réinitialisation des settings d’accès aux api green.
Ajouter les unités dans la preview du CarbonBot et changer le 0 en O du C02.
Ajout des traductions pour les associations de type Autre et Social.
Problème de stats qui commencent à minuit le jour même à la place de l’heure exacte.

4.7.1 – 14.10.2021

Arrondir et mettre en avant le bilan carbone sur la page de confirmation de commande.
Le bilan carbone n’est pas affiché en gras si le CarbonBot n’est pas activé.

4.7.0 – 13.10.2021

Création d’une page de gestion du compte API Charity.
Affichage d’un bloc CharityKit sur la home page du module.
Ajout d’une page de configuration pour le produit CharityKit.
Affichage du bloc de présentation de CharityKit.
Affichage du popin avec la liste des associations.
Permettre d’annuler un don.
Enregistrement des dons validés.
Afficher les statistiques simplifiées des dons sur la page d’accueil du module.
Permettre le tri des partenariats dans le backoffice du module.
Gestion des traductions dynamiques du CharityKit.
Afficher un message “Mode test activé” dans le CarbonBot.
Afficher une notification permanente pour indiquer que la période de test est expirée.
Améliorer l’affichage du “Mode test activé”.
Déplacer les champs ‘Nom du serveur’ des différents produits dans la page de Support.
Correction de l’utilisation du HookHandler.
Suppression de l’injection d’un Behavior obsolète.
Correction de l’affichage des Outputs sur la page de checkout.
Correction d’un warning sur la page de création d’un bouton de paiement.
Correction d’un prolbème de gestion du produit de don lors d’une activation sur le réseau.
Correction d’un bug au niveau du chargement des variables javascript.
Correction d’un problème lors de l’upgrade du module vers la 4.7.0.
Correction du type de curseur sur les boutons du popin des associations.
Ajout des traductions manquantes sur le bloc CharityKit de la home page du module.
Modification du comportement lors de la ‘revalidation’ d’un don.
Problème de défilement de la page lors de l’ouverture du popin Charity.
Améliorer l’affichage du bouton d’annulation du don.
Suppression de la possibilité d’ajouter manuellement des dons dans le panier via la fiche produit.
Désactivation soft de ClimateKit par défaut.
Correction de l’absence de notification sur les pages du CharityKit pour inviter à se connecter.
Correction d’une erreur sur la page de gestion des partenariats lorsqu’on était pas connecté.
Problème d’affichage de l’image du CharityGift.
Erreur lors de l’upgrade permettant de corriger le setting ‘tree_api_server’.
Problème de synchronisation des produits avec la version 1.7.7 de Prestashop.
Retirer la double utilisation de la classe URLSearchParams.
Correction de la rotation du loader du Carbon Bot.
Problème de cache avec les traductions.
Catcher les erreurs de mot de passe incorrects avec les API greens.
Corriger les liens externes situés dans les headers de la page d’accueil.
La page de config du ClimateKit n’est pas disponible tant qu’aucun mandat SEPA n’est signé.
Présence de blocs vides sur la page d’accueil lorsqu’on n’est pas connecté a Climate et Charity.
Correction orthographique de la description de la gestion des partenariats.
Correction orthographiques
Vérifier si un don existe déjà pour une commande avant de relancer le processus de validation du don.
Amélioration des scripts front pour les rendre pilotables.
Adaptation CSS.
Cacher le header quand on a qu’un seul bouton sur la page de Gestion des boutons de paiement.
Revoir l’affichage de la page de configuration du ClimateKit.
Amélioration de la gestion des Gift en cas de suppression manuelle.
Problème d’affichage du badge mode test sur la page de confirmation quand le carbonbot n’est pas activé.
Cacher le lien vers la page configuration du Charity dans le bloc charity sur la page d’accueil du backoffice.
Correction du build de la configuration des services.
Erreur sur la page d’accueil du module lorsque l’on est pas connecté à Charity.
Correction des traductions de la popin Charity.
Factoriser l’utilisation du Parser dans le service Translator.
Augmenter la durée du cache.

4.6.2 – 27.08.2021

4.6.1 – 28.07.2021

Ajouter la colonne ‘ID-tech’ dans le CSV d’export du catalogue produits.
Correction du problème de cache de transaction sur les paiements en XTIME.

4.6.0 – 26.07.2021

Permettre la surcharge du template de base utilisé sur le frontoffice.
Création du bloc de génération de l’export produit.
Cacher le bouton d’export si la clé ‘carbon_footprint_catalogue’ est vide.
Ajouter un bouton de vidange du cache sur la page de support.
Configurer un upgrade pour récupérer la valeur globale du setting “tree_api_server”
Problème de balisage sur le template du frontoffice.
Correction du setting “tree_api_server” qui n’est plus “global”.
Problème de nommage des services de filtrage.

4.5.0 – 21.07.2021

Baser l’activation du mode Insite sur le paramètre général.
Retirer le champ “Interface de paiement” du formulaire des boutons.
Création d’un template de ligne pour afficher un bouton de paiement de manière standardisée.
Afficher la liste des boutons sous forme de tableau.
Affichage d’une documentation détaillée de chaque mode de paiement.
Permettre d’ordonner les boutons par glissé/déposé.
Correction de la traduction manquante si l’export du catalogue produit échoue.
Chargement du fichier de style dédié au frontoffice.
Problème dans le template d’affichage d’une notification coté front.
Correction d’un problème de drag and drop sous Chrome.

4.4.2 – 12.07.2021

Rendre la server Bac à sable accessible depuis la version de production.

4.4.1 – 01.07.2021

Indication que l’export du catalogue produit vers l’api ClimateKit peut être très long.
Retirer le bouton d’export de la liste des produits vers l’api climatekit.
Correction d’un problème de string non-quotté dans les fichiers CSV générés.

4.4.0 – 30.06.2021

Renommer le ClimateKit en ClimateBot.
Ajout d’un message warning sur le booléan d’affichage de la page “en savoir plus”.
Séparation des gestions des traductions pour le CarbonBot.
Refonte du design du carbon bot.
Ajout d’un preview pour le CarbonBot.
Preview de la position et de la forme des angles du CarbonBot.
Preview de la couleur du CarbonBot.
Implémentation de l’export du catalogue produit.
Preview de l’affichage du lien “En savoir plus” dans le CarbonBot.
Ajout de l’animation d’ouverture du CarbonBot.
Ajout d’un pour envoyer directement la liste des produits à l’api Climate.
Griser les éléments du CarbonBot ayant une valeur à zéro.
Calculer l’estimation carbone des produits du panier.
Intégration du design de la partie mobile du CarbonBot et possibilité de le cacher sur mobile.
Supprimer la possibilité de modifier le mode test.
Modifications de quelques textes en rapport avec le CarbonBot.
Déplacement du champs de configuration de l’url vers la page “En savoir plus” dans le formulaire de configuration global.
Correction d’une erreur lors de l’injection de DataResource de type booléen.
Améliorer le hook StaticFiles pour que le canal ‘FRONT’ ne s’affiche pas sur la page de connexion.
Correction d’un problème d’export des booléens sur le front.
Correction de la gestion du hover sur le bouton d’ouverture du carbon bot.
Refonte du css du CarbonBot pour être le plus indépendant possible du CMS et du thème utilisé.
Correction de l’erreur 422 en cas de mise à jour d’un impacte transport déjà défini.
Blocage de la page en cas d’erreur sur le chargement du CarbonBot.
Problème de traduction sur la page de gestion du compte ClimateKit.
Gestion des erreurs lors du calcul du transport.
Définir la valeur par défaut pour les OutputBuilder non-conformes.
Correction d’un problème du calcul de la compensation carbone à cause d’erreurs liées à l’interface Shopable.
Amélioration de la gestion des retours en cas de suppression d’une collection.
Problème de IdFootprint introuvable.
Problème d’affichage du bilan carbon global dans le CarbonBot.
Affichage de l’empreinte carbone à la place de la compensation carbone sur la page de succès.
Correction des traductions du bilan carbone sur la page de succès.
Correction du mode de création d’un dossier de compensation carbone.
Ouverture le lien ‘en savoir plus’ du CarbonBot dans un nouvelle onglet.
Retouches CSS sur le CarbonBot.
Correction d’un problème au niveau de l’affichage du CarbonBot sur mobile.
Correction des boutons d’export et de téléchargement du catalogue produite qui ne fonctionnent plus.
Correction de l’affichage du formulaire de configuration générale de ClimateKit.
Sécuriser le listener FOTreeServicesListenersCarbonFootprintFinalization en cas d’erreur.
Les champs “nom d’utilisateur” et “compte” du formulaire de connexion ClimateKit sont inversés.

4.3.0 – 06.05.2021

Ajout d’un warning pour rappeler que l’affichage du footer dépend du thème utilisé.
Ajout du disclaimer statistiques sur la page d’accueil.
Suppression de la page “statistiques” de l’onglet ClimateKit.
Ajout d’un lien vers le backoffice ClimateKit.
Correction d’un problème d’affichage du bilan carbone avec les versions de WooCommerce antérieure à la 3.7.0.
Correction d’un problème d’affichage des blocs de gestion des extensions et modification des classes css permettant de configurer la taille d’un bloc.
Affichage des boutons de paiement lorsqu’un produit n’a pas de catégorie.
Sur la page d’accueil, placer tout en bas le block indiquant que l’on peut gérer ses extensions via la page dédiée.
Correction de la méthode de stockage des données de statistiques, utilisation de DataResource au lieu de cookie.
Vérifier si il s’agit d’une requête ajax avant de charger les fichiers statiques.
Renommer le concept d”extension’ en ‘produit’.
Renommer le wording du plugin ClimateKit.
Modification de l’affichage des crédentials de connexion au compte ClimateKit.

4.2.1 – 05.05.2021

Correction de la configuration des clients Curl.
Correction de la gestion de l’orderId avec l’API de paiement.

4.2.0 – 22.04.2021

Envoie des adresses client à l’API de paiement.
Correction de la récupération de l’adresse de livraison.
Correction de la configuration de l’url de retour utilisée en cas d’erreur lors de la création d’un paiement.
Complétion des entêtes envoyées par le Requester Fopen.
Correction du statut final utilisé pour cloturé un dossier de paiement ClimateKit.

4.1.3 – 20.04.2021

Ajout d’une note dans une commande dont le paiement a été refusé.
Correction du type de la colonne ‘filtered_category_primaries’ de l’entité Button.
Correction de l’injection du script ClimateKit sur le frontoffice.
Suppression de l’upgrade 4.1.1 problématique.

4.1.2 – 15.04.2021

Ajout d’explications détaillées sur la page de filtrage d’un bouton de paiement.
Correction d’un problème de typage lors de l’enregistrement de l’empreinte carbone.
Correction de la configuration de l’entité Transaction causant un blocage des remboursements.
Correction des traductions manquantes en cas de paiement refusé.

4.1.1 – 23.03.2021

Correction du traitement des commandes en état d’erreur.
Correction du wrapper superglobal des sessions.
Correction de la taille du champ ‘filtered_category_primaries’ de l’entité Button.
Utilisation de l’index d’autoloading pré-compilé.
Utilisation d’un includer pré-compilé.

4.1.0 – 23.03.2021

Ajout d’une page permettant de configurer le filtrage de chaque bouton de paiement.
Possibilité de filtrer un bouton par catégorie de produit.
Ajout des traductions manquantes sur la page de notification du frontoffice.
Ajout des traductions manquantes pour la configuration de la reconstitution manuelle du panier.
Utilisation de la route /availablepaymenttype pour la récupération des moyens de paiement.

4.0.3 – 15.02.2021

Validation des commandes en état d’erreur.
Vidange du cache lors de la modification des identifiants de l’API de paiement.

4.0.2 – 10.03.2021

Correction du diagnostique d’activation du gateway lors d’une mise-à-jour automatique.

4.0.1 – 09.03.2021

Correction du diagnostique d’activation du gateway lors d’une mise-à-jour automatique.

4.0.0 – 05.03.2021

Installation de l’extension ClimateKit.
Ajout d’un diagnostique pour vérifier l’activation du module PayGreen dans WooCommerce.
Affichage de l’impacte carbone d’une commande.
Affichage de la compensation carbone à la fin du processus de paiement.
Ajout de plusieurs pages permettant la connexion à un compte ClimateKit.
Mise à jour des images par défaut des boutons de paiements PayGreen.
Renommage du moyen de paiement Lunchr en Swile.
Affichage des boutons de paiements seulement si la devise sélectionée est supportée par PayGreen.
Affichage des release-notes dans le backoffice du module.
Gestion des incohérences dans les limitations de montant de panier d’un bouton de paiement.
Affichage d’un warning si un bouton de paiement en plusieurs fois est configuré avec plus de 4 versements.
Meilleur explication du caractère global des paramètres de configuration de la page ‘Support’.
Demande de confirmation avant l’effacage d’un fichier de log.
Correction des tables SQL sans prefixe.
Vérification de la devise utilisée avant d’afficher les boutons de paiement.
Correction des paiements suspects en cas de transaction composite.
Correction d’un bug dans la gestion des montants éligibles en environnement multi-boutiques.
Correction d’un bug lors de la confirmation des paiements TOKENIZE.
Affichage d’une notification à l’utilisateur en cas d’erreurs lors de la connexion OAuth plutôt qu’une exception.
Correction d’un bug sur le formulaire de modification des boutons, un nouveau bouton était créé lors de la validation du formulaire.
Correction du lien permettant d’afficher les release-notes au delà de 5.
Correction de l’url du serveur ClimateKit de production.
Corrections divers sur la page d’affichage des release-notes.
Utilisation systématique du LocalHandler pour récupérer la locale.

3.2.7 – 10.02.2021

Correction d’un problème de paiement indisponible via un lien de paiement créé par le CMS.
Correction des retours clients après payment TRD non-basés sur un PaymentRecord.

3.2.6 – 08.12.2020

Prise en compte des répertoires wp-content personnalisés.
Amélioration de la compatibilité avec les transactions générées avec l’ancienne URL du frontoffice.
Correction d’un problème lors du téléchargement du framework PayGreen.
Correction de la taille des logos PayGreen.

3.2.5 – 05.11.2020

Consolidation du script JS de calcul de l’impacte carbone en cas de concaténation des fichiers statiques.
Correction d’une erreur qui empêchait l’envoi des données Tree avec le navigateur Chrome.

3.2.4 – 14.10.2020

Correction d’un problème lors de la restauration des boutons de paiements.
Réutilisation de la constante DEFAULT_PICTURE pour assurer la compatibilité avec les anciennes versions.

3.2.3 – 14.10.2020

Correction d’un problème de compatibilité avec le plugin ‘Elementor’.

3.2.2 – 08.10.2020

3.2.1 – 06.10.2020

Correction d’un bug lorsque l’IPN était reçu trop rapidement.
Correction d’une erreur qui générait une nouvelle transaction malgré un PID déjà existant.
Correction d’erreurs sur le composant ResourceBag.

3.2.0 – 06.10.2020

Ajout d’une preview de l’image dans le formulaire de création d’un bouton de paiement.

3.1.4 – 01.10.2020

Correction d’un bug qui pouvait générer de mauvaises URL pour certains endpoints.
Correction d’une erreur lors de la récupération du ‘carrier’ durant le calcul de l’empreinte carbone.
Correction d’une erreur avec des commandes ayant le statut ‘WAITING’.
Correction d’une erreur lors de l’enregistrement d’images via le module.
Réduction du temps du PID Locking: 30sec -> 3sec.

3.1.3 – 30.09.2020

Améliorations mineures.
Correction d’un bug lors de la redirection après la validation d’une commande.
Correction d’une erreur avec des commandes ayant le statut ‘waiting’.
Prise en compte des traductions enregistrées dans des sous-répertoires.
Correction d’un bug avec les path absolus de l’autoloader.
On affiche plus la balise ‘ul’ de notifications si il n’y a pas de notifications.

3.1.2 – 25.09.2020

Améliorations mineures.
Amélioration des logs sur la page de paiement.

3.1.1 – 24.09.2020

Améliorations mineures.
Correction d’un bug lié à une mauvaise gestion du cache Smarty.

3.1.0 – 22.09.2020

Possibilité de traduire tous les éléments du front-office, ainsi que les libellés des boutons de paiement.
Le panier est désormais vidé suite à l’annulation d’une commande.
L’image d’un bouton de paiement aura pour hauteur sa hauteur naturelle si la configuration est définie à 0.
Ajout d’une page pour gérer les traductions.
Ajout d’un message de confirmation après la mise à jour d’un bouton de paiement.
Utilisation de l’anglais si on ne trouve pas une traduction.
Correction d’un warning qui apparaissait sur la page de paiement en mode Insite.
Correction d’un bug qui ne décochait pas tous les montants éligibles après configuration.
Correction de la gestion du timeout en cas d’erreurs. Limitation des forwards responses à 3.
Redirection vers la page de détails de la commande en cas d’order state inconnu.
Amélioration du cache Smarty.

3.0.20 – 18.09.2020

Traduction de la description du plugin.
Redirection vers la page de détails de la commande en cas d’order state inconnu.

3.0.19 – 09.09.2020

Internationalisation du frontoffice.
Ajout d’un selecteur de Shop dans le BO pour les CMS qui le requiert.
Correction d’un bug lié à la non prise en compte de la TVA sur les frais de livraisons.
Correction css mineure.
Correction de traductions.
Mauvaises variables utilisées dans le service RequestBuilder.

3.0.18 – 28.08.2020

Améliroations mineures.
Correction d’un bug lié à l’activation de Tree.

3.0.17 – 25.08.2020

Correction d’un bug lorsque le nom et prénom du Customer n’était pas correctement récupéré.

3.0.16 – 18.08.2020

Correction d’un bug lors de l’envoi de mail après une transaction.

3.0.15 – 13.08.2020

Correction de l’order state label “Autorisation de paiement accordée” -> “Prélèvement en attente”.

3.0.14 – 10.07.2020

Correction css mineure.
Correction du Chmod utilisé lors du téléchargement d’images.

3.0.13 – 19.06.2020

Améliorations mineures.

3.0.12 – 16.06.2020

Correction d’une erreur de droits en écriture sur le serveur wordpress.com

3.0.11 – 15.06.2020

Les fichiers de logs sont désormais stockés dans un sous-répertoire ‘log’ et non plus directement dans le répertoire ‘var’.
Affichage des paths importants sur la page ‘Informations système’ du backoffice.
Correction d’une erreur au niveau répertoire ‘var’ du CMS pendant l’installation du module.
Amélioration de la résilience du système de cache du module et de Smarty.
Amélioration de la résilience de l’autoloader.

3.0.10 – 12.06.2020

Correction du path vers le répertoire ‘var’ du CMS.

3.0.9 – 12.06.2020

3.0.8 – 08.06.2020

Mise à jour de la description du module.

3.0.7 – 02.06.2020

Correction du path vers le répertoire ‘var’ du CMS.
Amélioration de la gestion des settings.

3.0.6 – 27.05.2020

Création d’un affichage spécifique, lorsqu’un seul bouton de paiement est affiché.
Pré-selection du bouton de paiement PayGreen si il est le seul disponible.
Possibilité de configurer le titre affiché juste au dessus des boutons de paiements PayGreen.

3.0.5 – 27.05.2020

Améliorations mineures.

3.0.4 – 27.05.2020

Améliorations mineures.
Meilleure gestion des upgrades.

3.0.3 – 20.05.2020

Améliorations mineures.

3.0.2 – 20.05.2020

Corrections mineures.

3.0.1 – 20.05.2020

3.0.0 – 19.04.2020

Unification du backoffice.
Refonte du style global du module.
Mise à jour de la description du module.
Ajout de traductions.
Correction du processus d’upgrade du module.
Correction d’un bug lors de la restauration des boutons de paiements.
Correction d’un bug lié aux restrictions de montants sur le panier.
Correction d’un problème de style au niveau des boutons de paiements.
Correction d’un bug lié à une mauvaise URL retournée pour accéder au backoffice du module.
Correction de l’URL vers les fichiers statiques.
Correction de la gestion des settings.
Correction d’erreurs SQL.
Correction d’un bug lors de redirections.
Correction d’un bug lié à l’utilisation des backslashes.

2.2.10 – 05.03.2020

Correction d’un bug avec le client OAuth.

2.2.8 – 19.02.2020

Corrections d’un bug au niveau de la configuration interne du module.

2.2.7 – 26.11.2019

Corrections de plusieurs bugs.

2.2.6 – 05.06.2019

Activation des logs détaillés en production.
Augmentation de la limite de 25 caractères pour le label d’un bouton de paiement.

2.2.5 – 04.06.2019

Correction d’un bug au niveau de la prise en compte des variations de produits dans le montant éligible.
Correction d’un bug au niveau de l’Insite.

2.2.4 – 03.06.2019

Améliorations mineures.

2.2.3 – 29.05.2019

Corrections d’un bug sur le montant éligible des taxes.

2.2.2 – 17.04.2019

Corrections d’appels à des méthodes inexistantes.
Autres corrections mineures.

2.2.1 – 28.02.2019

Amélioration de l’Insite (taille dépendant des paramètres du paiement).
Correction d’un bug en mode Insite, lorsqu’on avait un seul bouton Paygreen.

2.2.0 – 19.02.2019

Gestion des montants éligibles.
Ajout d’une redirection si un utilisateur abandonne sa transaction.
Suppressions des usages de la short array syntax pour maximiser la compatibilité avec les anciennes versions de PHP.
Corrections css mineures.
Amélioration globale du fonctionnement interne du module.

2.1.6 – 04.01.2019

Correction d’un problème de date sur les paiements en plusieurs fois.

2.1.5 – 02.01.2019

Correction de la réduction de stock doublée.

2.1.4 – 28.12.2018

Changement de wording ‘Type de paiement’ -> ‘Moyen de paiement’.

2.1.3 – 27.12.2018

Possibilité de sélectionner son type de paiement lors de la création/modification d’un bouton de paiement.

2.1.2 – 27.12.2018

Corrections visuelles.

2.1.0 – 28.11.2018

Ajout du paiement Insite pour les boutiques HTTPS aillant le module Insite activé.
Ajout du détail des échéances sur le Insite.

2.0.6 – 21.11.2018

Correction d’une erreur dans le script greenprint.js.

2.0.5 – 21.11.2018

Correction d’un bug mineur même type de correctif que pour la release 2.0.4.

2.0.4 – 05.10.2018

Passage des déclarations avec [] en array pour les versions PHP en dessous de 5.4.

2.0.3 – 25.09.2018

Correction bug mineur d’affichage du logo PayGreen sur le moyen de paiement.

2.0.2 – 13.08.2018

Correction d’un bug mineur sur instanciation/suppression des boutons.

2.0.1 – 20.07.2018

Corrections de bugs mineurs.

2.0.0 – 12.07.2018

Ajout de la compensation carbone.
Ajout d’options supplémentaires pour les paiements en plusieurs fois / Abonnement
Possibilité d’ajouter un code promo pour un bouton.

1.4.5 – 13.12.2017

PayGreen ne s’affiche pas comme moyen de paiement si le panier ne réponds pas aux critères du ou des boutons.
Affichage du SIRET dans la configuration de la boutique.
Affichage du RIB dans la configuration de la boutique.
Résolution de nombreux bugs.

1.4.4 – 20.11.2017

1.4.3 – 28.09.2017

Correction d’un bug au retour de paiement avec des données en GET.

1.4.2 – 27.09.2017

Correction mineure.

1.4.1 – 26.09.2017

Correction de l’url utilisée pour garantir les paiements sécurisé.

1.4.0 – 25.09.2017

Nouvelle interface.
Ajout des paiement en plusieurs fois / Abonnement / à la livraison.
Ajout de PayGreen oAuth pour une configuration ultra rapide.
Résolution de nombreux bugs.

\n","description":"

Paygreen Impact, un module qui allie solidarité et soin de l’environnement, conçu pour s’intégrer à tous les parcours d’achat sans perturber votre tunnel de vente.

Ce que vous allez apprécier avec PayGreen Impact

✓ Une expérience d’achat solidaire et engagée !

✓ Le sentiment vrai d’avoir effectué un achat responsable

✓ Grâce à votre marque, les consommateurs connaissent enfin leur bilan carbone

✓ La possibilité d’une contribution climatique

✓ Valorisation de votre image de marque avec CharityKit et ClimateKit : deux outils qui permettent à vos clients d’arrondir leur panier au profit d’une association ou de compenser l’empreinte carbone de leur commande en ligne directement depuis la page de paiement.
\n100% des sommes sont reversées aux organismes concernés.

✓ Il choisit son impact, l’association et le montant de son arrondi solidaire

Offrez la meilleure expérience d’achat à vos clients

CharityKit et ClimateKit : des options qui donnent une dimension positive au paiement

Fonctionnalités

✓ Avec Climate Kit, présentez tout simplement à vos clients le bilan carbone de leur achat ! Mesurez et affichez en temps réel les émissions de GES générées par une commande sur votre site. Présentez l’évolution des émissions de CO2 de leur commande et proposez des actions de réduction et de contribution climatique.

✓ Avec CharityKit, transformez votre site de ventes en lieu de collecte. Bénéficiez des mêmes avantages qu’un mécène (sans engagement d’un minimum de collecte !) en associant votre image à diverses organisations en cohérence avec votre activité. L’Arrondi solidaire en ligne est un dispositif qui permet à vos clients d’arrondir leurs commandes au profit d’une association reconnue d’intérêt général. Associez votre image à ces associations, et engagez vos clients en un clic s’ils le souhaitent. 100% des dons sont reversés !

\n","screenshots":"

"},"short_description":"Paygreen Impact, un module qui allie solidarité et soin de l’environnement, conçu pour s’intégrer à tous les parcours d’achat sans perturber votre tun …","download_link":"https://downloads.wordpress.org/plugin/paygreen-impact.1.3.7.zip","screenshots":{"1":{"src":"https://ps.w.org/paygreen-impact/assets/screenshot-1.jpg?rev=2808091","caption":""},"2":{"src":"https://ps.w.org/paygreen-impact/assets/screenshot-2.jpg?rev=2808091","caption":""},"3":{"src":"https://ps.w.org/paygreen-impact/assets/screenshot-3.jpg?rev=2808091","caption":""},"4":{"src":"https://ps.w.org/paygreen-impact/assets/screenshot-4.jpg?rev=2808091","caption":""}},"tags":{"arrondi-en-ligne":"arrondi en ligne","compensation-carbone":"compensation carbone","impact":"impact","paygreen":"paygreen","rse":"rse"},"versions":{"1.0.0":"https://downloads.wordpress.org/plugin/paygreen-impact.1.0.0.zip","1.1.0":"https://downloads.wordpress.org/plugin/paygreen-impact.1.1.0.zip","1.1.1":"https://downloads.wordpress.org/plugin/paygreen-impact.1.1.1.zip","1.2.0":"https://downloads.wordpress.org/plugin/paygreen-impact.1.2.0.zip","1.3.0":"https://downloads.wordpress.org/plugin/paygreen-impact.1.3.0.zip","1.3.1":"https://downloads.wordpress.org/plugin/paygreen-impact.1.3.1.zip","1.3.2":"https://downloads.wordpress.org/plugin/paygreen-impact.1.3.2.zip","1.3.3":"https://downloads.wordpress.org/plugin/paygreen-impact.1.3.3.zip","1.3.4":"https://downloads.wordpress.org/plugin/paygreen-impact.1.3.4.zip","1.3.5":"https://downloads.wordpress.org/plugin/paygreen-impact.1.3.5.zip","1.3.6":"https://downloads.wordpress.org/plugin/paygreen-impact.1.3.6.zip","1.3.7":"https://downloads.wordpress.org/plugin/paygreen-impact.1.3.7.zip","trunk":"https://downloads.wordpress.org/plugin/paygreen-impact.zip"},"donate_link":"","icons":{"1x":"https://ps.w.org/paygreen-impact/assets/icon-256x256.jpg?rev=2808091","2x":"https://ps.w.org/paygreen-impact/assets/icon-256x256.jpg?rev=2808091"}}]

equivalence surcharge

Autonomos

Contasimple

PayGreen Impact

Get New Themes & Resources